-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Varnish k8s
plugin support
#1282
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor change before I approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm! (fix that problem caleb pointed out) ✅
9f59c3d
to
bf8ad4b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work ✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, just a documentation question from my end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thanks Austin! Forgot to approve in the morning so doing so now
…the nature of log collection
Head branch was pushed to by a user without write access
942d85a
to
0122f4a
Compare
Description
This PR updates the Varnish mixin to support the
k8s
pluginLogs for this integration required sidecar forwarding and having
alloy
read from an actual file on the container's filesystem, rather than reading logs from the container'sstdout
. With this, even though it'sk8s
we're still going to have afilename
label and it makes sense here.Changes